 |
| Test team must review the Feature Model to ensure that the features are free from inconsistencies and if the main dependencies are represented in the diagram. |
| Disciplines: Technical Reviews |
|
  Purpose
| The Feature model walkthrough is held to ensure adequacy, technical feasibility, completeness, as well as the
relationship among features. |
Relationships
| Roles | Primary Performer:
| Additional Performers:
|
| Inputs | Mandatory:
| Optional:
|
| Outputs |
|
Main Description
| In Feature Dependency Diagram walkthrough, the test team must review the Feature Dependency Diagram to ensure that
the dependecies match user needs, and are free from inconsistencies. It also improves the understanding of the
test and design team regarding which are the dependencies among features. After finishing the review, a detailed
report is generated that lists items of concern regarding the dependecies. Design team may also participate in this
activity. |
Steps
 Plan for a Feature Model Walkthrough
| This step serves as a guide to the feature model review activity. The plan is prepared in a meeting, in which the
review goals are established, as well as roles (basically: review leader [who will coordinate the review], author [one who
produced the artifact under review], reviewers, and recorder [responsible for the review report]), team size and the right
participants, i.e. stakeholders, are defined. |
Prepare Feature Model walkthrough
The responsible group for building the feature model, as being very familiar with the item under review, is
nominated the author. Its responsibility includes preparing a skilled presentation of the material aimed
at making the remaining team members able to build a comprehensive mental model of the item so that it is
possible to both evaluate its quality and detect defects.
Another in the team is nominated the review leader, who will actually later coordinate the progression of the
review.
|
Conduct Feature Model Walkthrough
In this step a meeting which the involved stakeholders will be held. The coordinator chairs the meeting.
In this meeting, the feature model author(s) is(are) supposed to present the material, without influencing the
reviewers into making the same logical errors as he did. The reviewers can discuss the documentation in
order to make suggestions where the material seems flawed or has potential for extension. If, during the
presentation, things are not clear enough, team members are allowed to ask questions in order to clarify aspects of the
presented material.
Reviewers must observe specific elements of the feature model, including aspects of variability, relationships,
etc, according to the checklist provided.
It is critical that the group remains focused on the task they are involved with. The coordinator can help in this
process by restraining unnecessary discussions and lead the group in the right direction. Moreover, the Coordinator
should resolve disagreements when the team can not reach a consensus.
|
Report the findings
After conducting the walthrough, all attendees must decide whether to accept/reject modifications in the artifact as
well as accept/reject the overall artifact. It will base the walkthrough report to be then produced.
A detailed report (Validation Report), including information regarding what was reviewed,
who reviewed, and what are the findings of the review is generated. It lists items of
concern regarding the requirements and use cases, i.e. problem areas within the product and corrections to be
made.
The Validation Report Template is available in Guidance folder.
|
|
Key Considerations
The major purpose here is to find defects. However, there may be times when participants drift from the main
purpose. The review leader, i.e. the moderator, needs to prevent this from happening and ensure that the
walkthrough focuses on the defects or weaknesses rather than identifying fixes or resolutions.
It is recommended to apply a time-box mode for the walkthrough. This will be helpful to avoid time wasting and/or
effectiveness loss.
|
|
Display views
